Methods and apparatuses for reconfiguring a data connection

ABSTRACT

Apparatuses, methods, and systems are disclosed for reconfiguring a data connection using new parameters. One apparatus includes a processor and transceiver that communicates with a mobile communication network. The processor establishes a data connection with the mobile communication network using a first set of parameters and receives a second set of parameters from the mobile communication network with an indication of how at least one parameter in the first set corresponds to at least one new parameter in the second set. The processor further determines a third set of parameters from the first set of parameters and the second set of parameters and reconfigures the data connection using the third set of parameters.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to reconfiguring a dataconnection using new parameters.

BACKGROUND

The following abbreviations and acronyms are herewith defined, at leastsome of which are referred to within the following description.

Third Generation Partnership Project (“3GPP”), Positive-Acknowledgment(“ACK”), Access and Mobility Management Function (“AMF”), Common ControlPlane Network Function (“CCNF”), Control Plane Function (“CPF”), DataNetwork Name (“DNN”), Downlink (“DL”), Enhanced Mobile Broadband(“eMBB”), Evolved Node B (“eNB”), European Telecommunications StandardsInstitute (“ETSI”), Hybrid Automatic Repeat Request (“HARQ”),Internet-of-Things (“IoT”), Internet Protocol (“IP”), Long TermEvolution (“LTE”), LTA Advanced (“LTE-A”), Medium Access Control(“MAC”), Machine Type Communication (“MTC”), Massive IoT (“mIoT”),Massive MTC (“mMTC”), Narrowband (“NB”), Negative-Acknowledgment(“NACK”) or (“NAK”), Network Function (“NF”), Network Slice Instance(“NSI”), Network Slice Selection Assistance information (“NSSAI”),Network Slice Selection Function (“NSSF”), Network Slice SelectionPolicy (“NSSP”), Next Generation Node B (“gNB”), Non-Access Stratum(“NAS”), Primary Cell (“PCell”), Public Land Mobile Network (“PLMN”),Quality of Service (“QoS”), Radio Access Network (“RAN”), Radio ResourceControl (“RRC”), Receive (“RX”), Session Management (“SM”), SessionManagement Function (“SMF”), Secondary Cell (“SCell”), Single NSSAI(“S-NSSAI”), Slice Differentiator (“SD”), Slice/Service Type (“SST”),Transmission Control Protocol (“TCP”), Transmission and Reception Point(“TRP”), Transmit (“TX”), Uplink Control Information (“UCI”), UserDatagram Protocol (“UDP”), User Entity/Equipment (Mobile Terminal)(“UE”), Uplink (“UL”), User Plane Function (“UPF”), Universal MobileTelecommunications System (“UMTS”), Ultra-reliability and Low-latencyCommunications (“URLLC”), and Worldwide Interoperability for MicrowaveAccess (“WiMAX”). As used herein, “HARQ-ACK” may represent collectivelythe Positive Acknowledge (“ACK”) and the Negative Acknowledge (“NAK”).ACK means that a TB is correctly received while NAK means a TB iserroneously received.

In 5G networks, network slicing allows a network operator to divide thecommunication network into finer, small networks optimized for certainfeatures. A UE may be configured with network slice relevantinformation, such as a network slice selection policy (“NSSP”), used toselect a particular network slice. During an initial UE configuration(e.g., first powering on with a new (U)SIM card), the Home Public LandMobile Network (H-PLMN) operator can configure the UE with the NSSPpolicy for the HPLMN itself and for particular other PLMNs (e.g.,Equivalent PLMNs or other visited PLMNs). However, a NSSP static orsemi-static and becomes unsuitable if a network configuration changes, anetwork policy changes, or a UE subscription changes.

BRIEF SUMMARY

Methods for reconfiguring a data connection using new parameters aredisclosed. Apparatuses and systems also perform the functions of themethods. One method of a UE for reconfiguring a data connection usingnew parameters includes establishing a data connection with a mobilecommunication network using a first set of parameters and receiving asecond set of parameters from the mobile communication network and anindication of how at least one parameter in the first set of parameterscorresponds to at least one new parameter in the second set. The methodalso includes determining a third set of parameters from the first setof parameters and the second set of parameters and reconfiguring thedata connection using the third set of parameters.

One method of a network function for re-registering a remote unit usingnew parameters includes registering a remote unit with a mobilecommunication network using a first set of parameters and identifying asecond set of parameters to be used by the remote unit in the mobilecommunication network. The method also includes sending a second set ofparameters to the remote unit and an indication of how the at least oneparameter in the first set of parameters corresponds to at least one newparameter in the second set and receiving a message from the remote unitcontaining a third set of parameters for registering with the mobilecommunication network. Here, the third set of parameters is based on thefirst set of parameters and the second set of parameters.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for reconfiguring a data connection usingnew parameters;

FIG. 2 is a block diagram illustrating one embodiment of a networkarchitecture for reconfiguring a data connection using new parameters;

FIG. 3 is a schematic block diagram illustrating one embodiment of aremote apparatus for reconfiguring a data connection using newparameters;

FIG. 4 is a schematic block diagram illustrating one embodiment of anetwork function apparatus for re-registering the remote unit using newparameters;

FIG. 5 is a block diagram illustrating one embodiment of a networkprocedure for reconfiguring a data connection using new parameters;

FIG. 6 is a schematic flow diagram illustrating one embodiment of amethod reconfiguring a data connection using new parameters; and

FIG. 7 is a schematic flow chart diagram illustrating one embodiment ofa method for re-registering a remote unit using new parameters.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects.

For example, the disclosed embodiments may be implemented as a hardwarecircuit comprising custom very-large-scale integration (“VLSI”) circuitsor gate arrays, off-the-shelf semiconductors such as logic chips,transistors, or other discrete components. The disclosed embodiments mayalso be implemented in programmable hardware devices such as fieldprogrammable gate arrays, programmable array logic, programmable logicdevices, or the like. As another example, the disclosed embodiments mayinclude one or more physical or logical blocks of executable code whichmay, for instance, be organized as an object, procedure, or function.

Furthermore, embodiments may take the form of a program product embodiedin one or more computer readable storage devices storing machinereadable code, computer readable code, and/or program code, referredhereafter as code. The storage devices may be tangible, non-transitory,and/or non-transmission. The storage devices may not embody signals. Ina certain embodiment, the storage devices only employ signals foraccessing code.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random-access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. This code may be provided to a processor of ageneral-purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the schematic flowchartdiagrams and/or schematic block diagrams.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus, orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theschematic flowchart diagrams and/or schematic block diagram.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods, and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, segment, or portion of code, which includes one ormore executable instructions of the code for implementing the specifiedlogical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

In order to provide dynamic NSSAI configuration in a UE, a network maydetermine that one or more parameters in a first set of parameters(e.g., used to register a UE and/or establish a data connection) is notvalid for a current network slice instance. The network then provides asecond set of parameters, whereby the UE may reconfigure its dataconnection and/or reregister with network. The network may also sendassistance and information to indicate how the new set of parameters isto be used.

FIG. 1 depicts a wireless communication system 100 for reconfiguring adata connection using new parameters, according to embodiments of thedisclosure. In one embodiment, the wireless communication system 100includes remote units 105, base units 110, and communication links 115.Even though a specific number of remote units 105, base units 110, andcommunication links 115 are depicted in FIG. 1, one of skill in the artwill recognize that any number of remote units 105, base units 110, andcommunication links 115 may be included in the wireless communicationsystem 100.

In one implementation, the wireless communication system 100 iscompliant with the 5G system specified in the 3GPP specifications. Moregenerally, however, the wireless communication system 100 may implementsome other open or proprietary communication network, for example, LTEor WiMAX, among other networks. The present disclosure is not intendedto be limited to the implementation of any particular wirelesscommunication system architecture or protocol.

In one embodiment, the remote units 105 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), smart appliances (e.g.,appliances connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), or thelike. In some embodiments, the remote units 105 include wearabledevices, such as smart watches, fitness bands, optical head-mounteddisplays, or the like. Moreover, the remote units 105 may be referred toas subscriber units, mobiles, mobile stations, users, terminals, mobileterminals, fixed terminals, subscriber stations, UE, user terminals, adevice, or by other terminology used in the art. The remote units 105may communicate directly with one or more of the base units 110 viauplink (“UL”) and downlink (“DL”) communication signals. Furthermore,the UL and DL communication signals may be carried over thecommunication links 115.

The base units 110 may be distributed over a geographic region. Incertain embodiments, a base unit 110 may also be referred to as anaccess terminal, a base, a base station, a Node-B, an eNB, a gNB, a HomeNode-B, a relay node, a femtocell, an access point, a device, or by anyother terminology used in the art. The base units 110 are generally partof a radio access network (“RAN”) that may include one or morecontrollers communicably coupled to one or more corresponding base units110. These and other elements of radio access network are notillustrated but are well known generally by those having ordinary skillin the art. The base units 110 connect to the mobile core network 130via the RAN.

The base units 110 may serve a number of remote units 105 within aserving area, for example, a cell or a cell sector via a wirelesscommunication link. The base units 110 may communicate directly with oneor more of the remote units 105 via communication signals. Generally,the base units 110 transmit downlink (“DL”) communication signals toserve the remote units 105 in the time, frequency, and/or spatialdomain. Furthermore, the DL communication signals may be carried overthe communication links 115. The communication links 115 may be anysuitable carrier in licensed or unlicensed radio spectrum. Thecommunication links 115 facilitate communication between one or more ofthe remote units 105 and/or one or more of the base units 110.

In one embodiment, the mobile core network 130 is a 5G core (“5GC”),which may be coupled to a data network 160, like the Internet andprivate data networks, among other data networks. In some embodiments,the remote units 105 communicate with a remote host 165 via a networkconnection with the mobile core network 130. Each mobile core network130 belongs to a single public land mobile network (“PLMN”). The presentdisclosure is not intended to be limited to the implementation of anyparticular wireless communication system architecture or protocol.

The mobile core network 130 includes several network functions (“NFs”)and multiple network slices 155. As depicted, the mobile core network130 includes at least one access and mobility management function(“AMF”) 135, at least one session management function (“SMF”) 140, atleast one user plane function (“UPF”) 145, and at least one networkslice selection function (“NSSF”) 150. Although a specific number of NFsare depicted in FIG. 1, one of skill in the art will recognize that anynumber of NFs may be included in the mobile core network 130.

The AMF 135 and SMF 140 are examples of control plane network functionsof the mobile core network 130. Control plane network functions provideservices such as UE registration, UE connection management, UE mobilitymanagement, data session management, and the like. The UPF 145 providesuser plane (e.g., data) services to the remote units 105. For example, adata connection between the remote unit 105 and a remote host 165 ismanaged by a UPF 145.

The NSSF 150 selects a proper network slice 155 (and a network sliceinstance) for a particular UE connection. The NSSF 150 may be astand-alone NF or co-located with the AMF 135 or another NF (e.g., aNRF, or a PCF). The network slices 155 are logical networks within themobile core network 130. The network slices 155 are partitions ofresources and/or services of the mobile core network 130. Differentnetwork slices 155 may be used to meet different service needs (e.g.,latency, reliability, and capacity). Examples of different types ofnetwork slices 155 include enhanced mobile broadband (“eMBB”), massivemachine-type communication (“mMTC”), and ultra-reliability and lowlatency communications (“URLLC”). A mobile core network 130 may includemultiple network slice instances of the same network slice type.

As depicted, a remote unit 105 may access the mobile core network 130(including a particular network slice 155 of the mobile core network130) via base unit 110. However, due to its mobility, the remote unit105 may move a portion of the network topology where prior network slice155 instance is no longer available. Here, one or more parameters usedestablish a data connection (e.g., with the SMF 140) may become invalidand a data connection terminated. As described in greater detail below,the AMF 135 may communicate new parameters to the remote unit 105,wherein the remote unit 105 re-establishes the data connection using thenew parameters.

FIG. 2 depicts a network architecture 200 used for reconfiguring a dataconnection using new parameters, according to embodiments of thedisclosure. The network architecture 200 may be a simplified embodimentof the wireless communication system 100. As depicted, the networkarchitecture 200 includes a UE 205, a 5G (R)AN 210, a first networkslice instance (here, “NSI-1”) 215, a second network slice instance(here, “NSI-2”) 220, and a set of common control plane network functions(“CCNFs”) 225. The set of common control plane network functions 225 mayinclude at least an AMF, a NSSF, and a UDM. Each network slice instancealso has dedicated network functions. Here, the first network sliceinstance 215 includes a control plane 230 with a first SMF 235 (“SMF-a”)and other dedicated network functions 240 and a first UPF 245 (“UPF-a”).Additionally, the second network slice instance 220 includes a controlplane 230 with a second SMF 250 (“SMF-b”) and other dedicated networkfunctions 240 and a second UPF 255 (“UPF-b”).

The UE 205 may be one embodiment of the remote unit 105 and the 5G (R)AN210 may include one or more base units 110, as described above. Thefirst and second network slice instances 215, 220 may be embodiments ofthe network slices 155. Additionally, the first and second SMFs 235, 250and the first and second UPFs 245, 255 may be embodiments of the SMF 140and UPF 145, respectively. The 5G (R)AN 210, the set of common controlplane network functions 225, and the network slice instances 215, 220(and their dedicated network functions) collectively form a mobilecommunication network with which the UE 205 communicates.

In the network architecture 200, the UE 205 may communicate with the 5G(R)AN 210 using a Uu interface, the 5G (R)AN 210 may communicate withthe set of common control plane network functions 225 using an N2interface and with the first and second UPFs 245, 255 using an N3interface. The first SMF 235 and the first UPF 245 may communicate usingan N4 interface. Likewise, the second SMF 250 and the second UPF 255 mayalso communicate using an N4 interface. The set of common control planenetwork functions 225 may communicate with the control planes 230 withinthe first and second network slice instances 215, 220 using an N11interface.

The UE 205 may be configured with network slice relevant information,which is referred as Network Slice Selection Assistance information(“NSSAI”). The NSSAI may consist of single or multiple S-NSSAIs (singleNetwork Slice Selection Assistance information). Each S-NSSAI includes aSlice/Service type (“SST,” referring to expected Network Slice behaviorin terms of features and services) and a Slice Differentiator (“SD,”which allows further differentiation for selecting an NSI from thepotentially multiple available NSIs complying with the SST).

In some embodiments, a network operator may provision the UE 205 with anetwork slice selection policy (“NSSP”). A NSSP includes one or moreNSSP rules with each rule associating an application with a certainS-NSSAI. When an application on the UE 205 associated with a specificS-NSSAI requests data transmission, then the UE 205 sends theapplication's user data using a PDU session established with theS-NSSAI. In certain embodiments, the application may provide a datanetwork name (“DNN”). In such embodiments, the UE 205 also considers theDNN when determining which PDU session (of potentially multiple PDUsession established with the S-NSSAI) to use.

Multiple network slice instances (“NSIs”) are deployed in the networkarchitecture 200, including the first NSI 215 and the second NSI 220. ANSI does not necessarily cover the whole PLMN area; rather, differentNSIs are deployed in different topological areas. The topological areacan be expressed in means of Tracking Area (“TA,” identified by aTracking Area Identifier, “TAI”) or list of Tracking Areas, or cell(identified by a cell ID) or list of cells. Generally, in a giventopological network area (e.g., TA, or list of TAIs, or cell, or list ofcell IDs) the configuration of deployed/instantiated NSI(s) does notchange. However, in another topological area the deployed NSI may bedifferent.

The association between S-NSSAI and NSI (in the network) is based onnetwork configuration and deployment. Such an association betweenS-NSSAI and NSI can change in time based on network reconfiguration orresource optimization. Different scenarios are possible for theassociation/relationship between S-NSSAI and NSI. In one embodiment,there may be a one-to-one mapping between S-NSSAI and NSI. In anotherembodiment, there may be multiple-to-one mapping between S-NSSAI andNSI. In yet another embodiment, there may be one-to-multiple mappingbetween S-NSSAI and NSI.

As depicted, the UE 205 exchanges signaling 260 with the set of commoncontrol plane network functions 225 (specifically with an AMF 135 withinthe set of common control plane network functions 225) in order toregister with the network (e.g., with a first set of one or moreS-NSSAIs), received new network parameters (e.g., a new S-NSSAI), andreregister with the network (e.g., using the new S-NSSAI), as describedherein. One or multiple of the NSIs serving the UE 205 may change due toseveral reasons (e.g., UE moving from old registration area to a newregistration area or network configuration change, etc.). The UE 205 isunaware about the configuration of NSIs in the old and new registrationareas. In order to inform the UE 205 of the change of NSIs, to which theUE 205 is associated, the network (e.g., an AMF in the set of commoncontrol plane network functions 225) assigns a new set of new parametersto the UE (e.g., changing the set of Allowed/Accepted S-NSSAIs) andfurther provides usage information that indicates to the UE 205 how touse the new set of parameters. As used herein, “usage information”refers to an indication of how the UE 205 is to use/apply the new set ofparameters. “Usage information” may also be referred to herein as“mapping indication” or “NSSAI assistance information.”

As discussed in further detail below, upon receiving a new set ofparameters and an indication of how to use the new set of parameters(e.g., receiving usage information for the new set of parameters), theUE 205 re-registers with the set of common control plane networkfunctions 225. Where a PDU session is established when the new set ofparameters is received, then the UE 205 may also re-establish the PDUsession using the new set of parameters (or establish a new PDU sessionusing the new set of parameters).

FIG. 3 depicts one embodiment of a remote apparatus 300 that may be usedfor reconfiguring a data connection using new parameters, according toembodiments of the disclosure. The remote apparatus 300 may be oneembodiment of the remote unit 105, the relay unit 120, the remote UE205, and/or the relay UE 210. Furthermore, the remote apparatus 300includes a processor 305, a memory 310, an input device 315, a display320, and a transceiver 325. In some embodiments, the input device 315and the display 320 are combined into a single device, such as atouchscreen. In certain embodiments, the remote unit 105 may not includeany input device 315 and/or display 320.

The transceiver 325 allows the remote apparatus 300 to communicate witha mobile communication network (e.g., a mobile core network 130 and/or anetwork slice instance 215, 220) over an access network (e.g., the baseunit 110 and/or 5G (R)AN 210). The transceiver 325 may include at leastone transmitter 330 and at least one receiver 335. Additionally, thetransceiver 325 may support at least one network interface 340 such as a“Uu” interface used to communicate with a base unit 110 or the 5G (R)AN210.

The processor 305, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 305 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 305 executes instructions stored in thememory 310 to perform the methods and routines described herein. Theprocessor 305 is communicatively coupled to the memory 310, the inputdevice 315, the display 320, and the transceiver 325.

In some embodiments, the processor 305 establishes a data connectionwith the mobile communication network using a first set of parameters.Here, the first set of parameters may include a network slice selectionparameter and a data network name. At some point after establishing thedata connection, the processor 305 receives a second set of parametersfrom the mobile communication network. Along with the second set ofparameters, the processor 305 receives an indication of how at least oneparameter in the first set (e.g., the set used to establish the dataconnection) corresponds to at least one new parameter in the second set.The processor 305 also determines a third set of parameters from thefirst set of parameters and the second set of parameters. The processor305 then controls the transceiver 325 to reconfigure the data connectionusing the third set of parameters.

In some embodiments, the processor 305 receives an indication that atleast one parameter in the first set (e.g., the set used to establishthe data connection) is no longer valid. For example, a messagecontaining the second set of parameters (and the indicator ofcorrespondence) may indicate that at least one parameter in the firstset is no longer valid. In one embodiment, receiving the indication thatat least one parameter in the first set is no longer valid includes theprocessor 305 receiving an indication that the data connection isdiscontinued (e.g., released).

In certain embodiments, reconfiguring the data connection may includethe processor 305 re-establishing the data connection using the thirdset of parameters. In one embodiment, re-establishing the dataconnection includes the processor 305 sending a non-access stratum(“NAS”) session management message that contains the third set ofparameters. In a further embodiment, re-establishing the data connectionincludes the processor 305 sending a session management (“SM”) message(e.g., a N1 Session Management Information message) encapsulated in aNAS transport message. Here, the NAS transport message contains thethird set of parameters and the N1 SM message, wherein the N1 SM messageincludes the at least one new parameter (e.g., a new S-NSSAI) from thesecond set of parameters.

In certain embodiments, reconfiguring the data connection includes oneof: the processor 305 re-establishing the data connection using thethird set of parameters, the processor 305 establishing a new dataconnection using a fourth set of parameters based on the second set ofparameters, and the processor 305 releasing the data connection. Forexample, the processor 305 may determine to release the data connectionin response to determining that the third set of parameters cannot becreated (e.g., results in an invalid combination/set of parameters).

In some embodiments, the first set of parameters includes a firstnetwork slice selection parameter. Here, the second set of parametersincludes one or more new network slice selection parameters. In oneembodiment, the processor 305 receives the indication of how the atleast one parameter in the first set corresponds to at least one newparameter in the second set by receiving usage information thatassociates the one or more new network slice selection parameters withone or more previously provided network slice selection parameters.Here, the one or more previously provided network slice selectionparameters includes the first network slice selection parameter. Incertain embodiments, the processor 305 further updates a network sliceselection configuration of the apparatus based on the one or more newnetwork slice selection parameters.

In some embodiments, the processor 305 sends a registration request toupdate the mobile communication network with a new registration area andreceives the second set of parameters in response to the registrationrequest. In such embodiments, receiving the second set of parameters andthe indication of how the at least one parameter in the first setcorresponds to at least one new parameter in the second set may includethe processor 305 receiving a registration accept message (e.g., a NASRegistration Accept message) that includes the second set of parametersand the indication of how the at least one parameter in the first setcorresponds to at least one new parameter in the second set.

In one embodiment, receiving the second set of parameters and theindication of how the at least one parameter in the first setcorresponds to at least one new parameter in the second set includes theprocessor 305 receiving a configuration update message. In anotherembodiment, receiving the second set of parameters and the indication ofhow the at least one parameter in the first set corresponds to at leastone new parameter in the second set includes the processor 305 receivinga NAS notification message. In yet another embodiment, receiving thesecond set of parameters and the indication of how the at least oneparameter in the first set corresponds to at least one new parameter inthe second set includes the processor 305 receiving a non-access stratum(“NAS”) Registration Accept message.

The memory 310, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 310 includes volatile computerstorage media. For example, the memory 310 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 310 includes non-volatilecomputer storage media. For example, the memory 310 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 310 includes bothvolatile and non-volatile computer storage media. In some embodiments,the memory 310 stores data relating to reconfiguring a data connectionusing new parameters, for example storing NSSP, Allowed NSSAI, and thelike. In some embodiments, the memory 310 also stores program code andrelated data, such as an operating system or other controller algorithmsoperating on the remote unit 105 and one or more software applications.

The input device 315, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 315 maybe integrated with the display 320, for example, as a touchscreen orsimilar touch-sensitive display. In some embodiments, the input device315 includes a touchscreen such that text may be input using a virtualkeyboard displayed on the touchscreen and/or by handwriting on thetouchscreen. In some embodiments, the input device 315 includes two ormore different devices, such as a keyboard and a touch panel.

The display 320, in one embodiment, may include any known electronicallycontrollable display or display device. The display 320 may be designedto output visual, audible, and/or haptic signals. In some embodiments,the display 320 includes an electronic display capable of outputtingvisual data to a user. For example, the display 320 may include, but isnot limited to, an LCD display, an LED display, an OLED display, aprojector, or similar display device capable of outputting images, text,or the like to a user. As another, non-limiting, example, the display320 may include a wearable display such as a smart watch, smart glasses,a heads-up display, or the like. Further, the display 320 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the display 320 includes one or more speakersfor producing sound. For example, the display 320 may produce an audiblealert or notification (e.g., a beep or chime). In some embodiments, thedisplay 320 includes one or more haptic devices for producingvibrations, motion, or other haptic feedback. In some embodiments, allor portions of the display 320 may be integrated with the input device315. For example, the input device 315 and display 320 may form atouchscreen or similar touch-sensitive display. In other embodiments,the display 320 may be located near the input device 315.

The transceiver 325 communicates with a mobile communication network viaan access network (e.g., a base unit 110 and/or the 5G (R)AN 210). Thetransceiver 325 operates under the control of the processor 305 totransmit messages, data, and other signals and also to receive messages,data, and other signals. For example, the processor 305 may selectivelyactivate the transceiver 325 (or portions thereof) at particular timesin order to send and receive messages. The transceiver 325 may includeone or more transmitters 330 and one or more receivers 335 forcommunicating over the access network. As discussed above, thetransceiver 325 may support one or more the network interfaces 340 forcommunicating with the mobile communication network (e.g., the base unit110 and various network functions in the mobile core network 130).

FIG. 4 depicts one embodiment of a network function apparatus 400 thatmay be used for reconfiguring a data connection using new parametersand/or re-registering a remote unit using the new parameters, accordingto embodiments of the disclosure. The network function apparatus 400 maybe one embodiment of the AMF 135. Furthermore, the network functionapparatus 400 includes a processor 405, a memory 410, an input device415, a display 420, and a transceiver 425. In some embodiments, theinput device 415 and the display 420 are combined into a single device,such as a touchscreen. In certain embodiments, the network functionapparatus 400 may not include any input device 415 and/or display 420.

The transceiver 425 allows the network function apparatus 400 tocommunicate with other network elements within a mobile communicationnetwork. As depicted, the transceiver 425 includes at least onetransmitter 430 and at least one receiver 435. Additionally, thetransceiver 425 may support at least one network interface 440 such asan “N2” interface used to communicate with a 5G (R)AN 210 and a “N11”interface used to communicate with control plane network functions, suchas the SMF 140.

The processor 405, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 405 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 405 executes instructions stored in thememory 410 to perform the methods and routines described herein. Theprocessor 405 is communicatively coupled to the memory 410, the inputdevice 415, the display 420, and the transceiver 425.

In some embodiments, the processor 405 registers the remote unit with amobile communication network using a first set of parameters. Here, theprocessor 405 may receive an initial registration message from theremote unit, the initial registration message containing a requested setof network slice selection parameters. In such embodiments, theprocessor 405 may return an allowed set of network slice selectionparameters to the remote unit. In certain embodiments, an allowed set ofnetwork slice selection parameters may include one or more defaultnetwork slice selection parameters. Here, returning the allowed set ofnetwork slice selection parameters includes the processor sending anindication that a default network slice selection parameter correspondsto one of: a data network name and a standardized network slice type.For example, a new S-NSSAI may have an PLMN-specific SST which maps to awell-known standardized SST.

At some point in time the processor 405 identifies a second set ofparameters to be used by the remote unit in the mobile communicationnetwork. Here, the second set of parameters corresponds to a change inthe network slice instance (“NSI”) of the remote unit. In oneembodiment, the NSI changes due to mobility of the remote unit. Forexample, the remote unit may move to a registration area thatcorresponds to the new NSI (e.g., in the network topology). In anotherembodiment, the change in NSI may be due to a change in the subscription(e.g., plan) of the remote unit or a network policy rule applicable tothe remote unit. Here, the change in subscription or policy may resultin the remote unit no longer being permitted to use an old NSI. In yetanother embodiment, the change in NSI may be due to a change in networkslice deployment within the mobile communication network. For example,the mobile communication network may bring on-line a new network slicethat serves an area where the remote unit it located.

When the NSI changes, one or more parameters in the first set ofparameters may no longer be valid. In such circumstance, the processor405 identifies the second set of parameters to be used by the remoteunit in the mobile communication network and sends the second set ofparameters to the remote unit with an indication of how the at least oneparameter in the first set of parameters corresponds to at least one newparameter in the second set. In one embodiment, the second set ofparameters includes the first set of parameters and one or moreadditional (new) parameters applicable to the new NSI. In anotherembodiment, the second set of parameters includes a subset of first setof parameters and one or more additional (new) parameters for to the newNSI that replace parameters in the first subset. In yet anotherembodiment, the second set of parameters may include a subset of firstset of parameters without any replacement parameters. Note that the sizeof the second set of parameters may be larger than, smaller than, or thesame size as the first set of parameters.

The indication of how the at least one parameter in the first set ofparameters corresponds to at least one new parameter in the second setinforms the remote unit how to use the second set of parameters based onknown usage information relating to the first set of parameters. Forexample, if “parameter-B” in the second set corresponds to “parameter-A”in the first set, then the remote unit knows that parameter-B may beused in the same circumstances where parameter-A might be used. Here itis assumed that the remote unit already knows when to use the first setof parameters prior to receiving the indication of how the at least oneparameter in the first set of parameters corresponds to at least one newparameter in the second set.

In response to sending the second set of parameters (and the indicationof correspondence) the processor 405 may receive a message from theremote unit containing a third set of parameters for registering withthe mobile communication network. Here, the third set of parameters isbased on the first set of parameters and the second set of parameters.

In one embodiment, identifying the second set of parameters may includethe processor 405 identifying the second set of parameters based on therequested set of network slice selection parameters (e.g., RequestedS-NSSAIs), subscribed parameters of the remote unit (e.g., SubscribedS-NSSAIs), and/or a network slice instance associated with the remoteunit. In another embodiment, identifying the second set of parametersincludes the processor 405 identifying the second set of parametersbased on a configuration of the remote unit and a network slice instancecurrently associated with the remote unit.

In some embodiments, the first set of parameters includes a firstnetwork slice selection parameter. Here, identifying the second set ofparameters may include the processor 405 identifying one or more newnetwork slice selection parameters for a network slice instancecurrently associated with the remote unit. Further, sending anindication of how the at least one parameter in the first setcorresponds to at least one new parameter in the second set may includethe processor 405 sending usage information that associates the one ormore new network slice selection parameters with one or more previouslyprovided network slice selection parameters, wherein the one or morepreviously provided network slice selection parameters includes thefirst network slice selection parameter.

In some embodiments, the processor 405 receives a registration requestfrom the remote unit and determines that at least one parameter in afirst set of parameters is no longer valid in response to theregistration request. In such embodiments, sending the second set ofparameters and the indication of how the at least one parameter in thefirst set corresponds to at least one new parameter in the second setmay include the processor 405 sending a registration accept message(e.g., a NAS Registration Accept message) that includes the second setof parameters and the indication of how the at least one parameter inthe first set corresponds to at least one new parameter in the secondset. The processor 405 may receive the registration request in responseto one of: the remote unit changing its registration area, the remoteunit changing its public land mobile network (“PLMN”) change, and theremote unit requiring temporarily use a network slice.

In certain embodiments, the processor 405 sends the second set ofparameters and the indication of how the at least one parameter in thefirst set corresponds to at least one new parameter in the second set bysending one of: a configuration update message and a NAS notificationmessage. In some embodiments, the processor 405 receives the messagefrom the remote unit containing the third set of parameters by receivinga session management (“SM”) request message encapsulated in a NAStransport message. Here, the NAS transport message contains the thirdset of parameters and the session management message and the SM requestmessage includes the at least one new parameter from the second set ofparameters.

In certain embodiments, the processor 405 may send a session managementSM request message to a SM function in response to determining that atleast one parameter in the first set is no longer valid. Here, the SMrequest message may include an indication to release an established dataconnection and a new network slice selection parameter from the secondset of parameters and the at least one new parameter included in thesession management message may be the new network slice selectionparameter. In further embodiments, the processor 405 further receives anSM response message from the SM function, the SM response messagecontaining a session release request message for the established dataconnection, with the processor 405 sending the session release requestmessage to the remote unit.

In some embodiments, the processor 405 identifies the second set ofparameters to be used by the remote unit in the mobile communicationnetwork by sending a query to a network slice selection function(“NSSF”) in response to receiving a registration request from the remoteunit. In such embodiments, the processor 405 may receive, from the NSSF,a mapping of network slice selection parameters to network sliceinstances. Here, identifying the second set of parameters furtherincludes the processor 405 identifying a set of allowed network sliceselection parameters based on a network slice instance currentlyassociated with the remote unit. Note that the NSSF may be a standaloneNF within the mobile communication network or may be a part of anotherNF, such as an NRF or PCF.

The memory 410, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 410 includes volatile computerstorage media. For example, the memory 410 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 410 includes non-volatilecomputer storage media. For example, the memory 410 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 410 includes bothvolatile and non-volatile computer storage media. In some embodiments,the memory 410 stores data relating to reconfiguring a data connectionand/or re-registering the UE using new parameters, for example storing aUE configuration, UE context, allowed NSSAI for UE, and the like. Incertain embodiments, the memory 410 also stores program code and relateddata, such as an operating system or other controller algorithmsoperating on the network function apparatus 400 and one or more softwareapplications.

The input device 415, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 415 maybe integrated with the display 420, for example, as a touchscreen orsimilar touch-sensitive display. In some embodiments, the input device415 includes a touchscreen such that text may be input using a virtualkeyboard displayed on the touchscreen and/or by handwriting on thetouchscreen. In some embodiments, the input device 415 includes two ormore different devices, such as a keyboard and a touch panel.

The display 420, in one embodiment, may include any known electronicallycontrollable display or display device. The display 420 may be designedto output visual, audible, and/or haptic signals. In some embodiments,the display 420 includes an electronic display capable of outputtingvisual data to a user. For example, the display 420 may include, but isnot limited to, an LCD display, an LED display, an OLED display, aprojector, or similar display device capable of outputting images, text,or the like to a user. As another, non-limiting, example, the display420 may include a wearable display such as a smart watch, smart glasses,a heads-up display, or the like. Further, the display 420 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the display 420 includes one or more speakersfor producing sound. For example, the display 420 may produce an audiblealert or notification (e.g., a beep or chime). In some embodiments, thedisplay 420 includes one or more haptic devices for producingvibrations, motion, or other haptic feedback. In some embodiments, allor portions of the display 420 may be integrated with the input device415. For example, the input device 415 and display 420 may form atouchscreen or similar touch-sensitive display. In other embodiments,the display 420 may be located near the input device 415.

The transceiver 425 communicates with one or more network functions of amobile communication network. The transceiver 425 operates under thecontrol of the processor 405 to transmit messages, data, and othersignals and also to receive messages, data, and other signals. Forexample, the processor 405 may selectively activate the transceiver (orportions thereof) at particular times in order to send and receivemessages. The transceiver 425 may include one or more transmitters 430and one or more receivers 435. As discussed above, the transceiver 425may support one or more the network interface 440 for communicating withthe one or more networks functions, such as an SMF 140.

FIGS. 5A and 5B depict a network procedure 500 for reconfiguring a dataconnection using new parameters, according to embodiments of thedisclosure. The network procedure 500 begins in FIG. 5A and continues inFIG. 5B. The network procedure 500 involves the UE 205, the 5G (R)AN210, the AMF 135, the first SMF (“SMF-a”) 235, the first UPF (“UPF-b”)245, the second SMF (“SMF-b”), and the second UPF (“UPF-b”). In certainembodiments, the network procedure 500 involves the NSSF 150; however,the NSSF 150 is optional.

The network procedure 500 begins at FIG. 5A with the UE 205 performingan initial registration with the AMF 135 (see block 502). In certainembodiments, the UE 205 sends a NAS Registration Request message andreceives a NAS Registration Accept message. During the InitialRegistration procedure (or Attach procedure), the UE 205 registers witha particular PLMN (e.g., with the mobile communication network) andobtain services from this network. The initial registration procedureincludes authenticating the UE 205, setting up required security for thecontrol plane and user plane, and the like.

When registering with the network, the UE 205 sends a Requested NSSAI tothe network. In certain embodiments, the AMF 135 (or optionally the NSSF150) stores the Requested NSSAI in a registration management (RM)context of the UE 205. In response, the AMF 135 sends an Allowed (akaAccepted) NSSAI to the UE 205. In certain embodiments, the AMF 135queries the NSSF 150 to determine the Allowed NSSAI for the UE 205. Insome embodiments, the network (e.g., AMF 135 and/or NSSF 150) considersthe configuration in the UE (e.g., Configured NSSAI per PLMN as part ofthe NSSP), if available, when determining the Allowed NSSAI for the UE.The set of Allowed S-NSSAIs is also stored in the AMF 135 with the UE205's RM context.

In certain embodiments, the NSSP (e.g., Configured NSSAI in the UE) ofthe UE 205 is not available in the network. For example, the AMF 135 (ora PCF) may not have information about the Configured NSSAI for a roamingUE 205. As another example, the UE 205 may not send a Requested NSSAI inthe NAS Registration Request message. In such embodiments, the AMF 135includes an Allowed NSSAI including one or multiple default S-NSSAI(s)in the NAS Registration Accept message to the UE 205. In case ofmultiple default S-NSSAIs, the NAS Registration Accept message mayinclude an indication (e.g., usage information) to the UE 205 how the UEshould use the default Allowed S-NSSAIs. Here, the usage information(indication) may indicate, a mapping of S-NSSAI to a subscribed DNN, ormapping of the S-NSSAI's SST value to well know standardized SST valuesknown at the UE, e.g., SST=“automotive” maps to SST=“V2X” because the UEdoes not understand “automotive” but does understand “V2X”.

For example, the AMF 135 may determine the need to send the additionalindication for the use of Allowed S-NSSAI (e.g., mapping of S-NSSAI toDNN) where a V-PLMN uses operator-specific values for the SST part ofthe S-NSSAI. As another example, the AMF 135 may determine the need tosend the additional indication for the use of S-NSSAI where there aremultiple S-NSSAIs having the same SST type and the SD parts might beambiguous in the UE 205. In yet another example, the usage informationindicates that the Allowed S-NSSAI (SST=“automotive”, SD=“Mercedes”)maps to the Requested S-NSSAI (SST=“V2X”, SD=“BMW”), or Allowed S-NSSAI(SST=“automotive”, SD=“car”) maps to the Requested S-NSSAI (SST=“V2X”,SD=“Mercedes”). The latter example shows 1-to-1 mapping. In stillanother example the mapping indication may be in 1-to-Many format, forinstance Allowed S-NSSAI (SST=“automotive”, SD=“car”) maps to RequestedS-NSSAI (SST=“V2X”, SD=“Mercedes”) and Requested S-NSSAI (SST=“mIoT”,SD=“Mercedes”). Please note that SST values, e.g. “V2X” or “automotive”or “mIoT”, can be represented by numerical values, e.g. “001”, “002”, inthe protocol implementation. Similar applies to the SD values, e.g.“car” or “Mercedes”, which can be represented also by numerical values.

After registering with the network, the UE 205 establishes a PDU sessionin order to send/receive data (e.g., IP data or non-IP data) via themobile communication network (see block 504). Here, the PDU session isestablished using a first set of parameters (e.g., S-NSSAI, DNN, SSCMode, PDU Type, etc.). For example, the first set of parameters mayinclude: [S-NSSAI-a, DNN-1, SSC1, PDU IP type, etc.]. Here, “S-NSSAI-a”is a first S-NSSAI that contains particular values for the [SST; SD]combination. In response to a PDU session establishment request with thefirst set of parameters, the AMF 135 and/or NSSF 150 assigns the NSI tobe used for this particular PDU session. In the depicted embodiment, theassigned NSI includes the first SMF 235 and the first UPF 245 to servethe PDU session of the UE 205. Referring back to FIG. 2, here theassigned NSI is the first NSI 215.

Referring again to FIG. 5A, at some point in time an event occurs whichrenders one or more of the parameter in the first set of parameters tobecome unavailable. The event may occur when the UE 205 is in aConnected state (e.g., CM-CONNECTED) or in an Idle state (e.g.,CM-IDLE). In certain embodiments, the event is initiated by the UE 205.For example, the UE 205 may move to a new registration area (see block506) which does not support all of the parameters in the first set(e.g., does not support the S-NSSAI-a) and the UE 205 sends aRegistration Request to update the network with its new registrationarea (see signaling 508). Here, the Registration Request includes theaforementioned Requested NSSAI. As another example, the UE 205 may moveto a new PLMN which does not support all of the parameters in the firstset (e.g., does not support the S-NSSAI-a).

In other embodiments, the event which renders the one or more parametersunavailable is a network-initiated event (see block 510). For example, asubscription of the UE 205 may change, where the new subscription doesnot allow the use of one or more parameters in the first set (e.g., doesnot support the S-NSSAI-a). As another example, a network policyapplicable to the UE 205 may change, where the new policy does not allowthe UE 2052 use one or more parameters in the first set (e.g., does notsupport the S-NSSAI-a). In yet another example, the deployment of NSIsmay change, where the new deployment does not support one or moreparameters in the first set (e.g., does not support the S-NSSAI-a).

In response to the event, the AMF 135 (and/or together with the NSSF150) determines that one or more parameters in the first set ofparameters used to establish the PDU session cannot be used anymore (seeblock 512). In doing so, the AMF 135 (and/or together with the NSSF 150)determines a Modification of the Set of Network Slice(s) for a UE (e.g.,for the UE 205). For example, the AMF 135 may determine that S-NSSAI-acannot be used in the new registration area of the UE 205. In certainembodiments, the UE 205's data connection (PDU session) may bediscontinued (e.g., released) as a result.

In some embodiments, the network determines that the set of networkslices with which the UE 205 is currently associated is modified. Thisdetermination may happen in a single NF (e.g., the AMF 135) or inmultiple NFs (including, e.g., the AMF 135, the NSSF 150, a PCF, a NRF,and the like). In one embodiment, this determination considers theconfiguration of the UE 205 (e.g., the Configured NSSAI per PLMN as partof the NSSP of the UE 205). In another embodiment, this determinationconsiders the Requested NSSAI stored the RM context of the UE 205 (ifavailable). In yet another embodiment, the determination considers boththe configuration of the UE 205 and the requested NSSAI.

If the network determines that one or multiple of the Allowed S-NSSAIsmay not be known in the UE 205, the serving PLMN provides additionalinformation how the new Allowed NSSAI is used in the UE 205 (e.g.,providing usage information mapping the new Allowed S-NSSAI(s) tocorresponding old Allowed S-NSSAI(s) or to corresponding old RequestedS-NSSAI(s)). The network (e.g., the AMF 135 and/or together with theNSSF 150) determines that one or multiple of the new Allowed S-NSSAIsmay not be known in the UE 205 based on the following mechanism.

The AMF 135 stores the Requested NSSAI from the initial Registrationprocedure and, together with the subscribed NSSAI, the AMF 135determines whether a particular new Allowed S-NSSAI to be provided tothe UE 205 is known in the UE 205 (e.g., whether a particular AllowedS-NSSAI is part of the UE 205's Configured NSSAI for this serving PLMN).Please note that in the serving PLMN, the set of Allowed S-NSSAIsprovided to the UE 205 may change after the time of registration (e.g.,due to UE mobility or changing network configuration). The network(e.g., the AMF 135 and/or together with the NSSF 150) determines the setof the Allowed S-NSSAIs based on the full set of the Requested S-NSSAIsand the subscribed S-NSSAIs. Please also note that one or multiple ofthe provided set of Allowed S-NSSAI(s) can have PLMN-specific SST valuesor SD values, which are unknown in the UE 205, as e.g., those S-NSSAI(s)are not part of the Configured S-NSSAI for this PLMN.

In certain embodiments, the network determines that the NSI to which theUE 205 is associated changes, but that there is no need for NSSAIre-configuration in the UE 205. For example, there may be no change tothe set of Allowed S-NSSAIs which have been provided to the UE despitethe change in NSI.

In some embodiments, the AMF 135 sends to the first SMF 235 (e.g.,SMF-a) an N11 SM Request message including a trigger to initiate a PDUSession Release procedure (see signaling 514). In certain embodiments,the AMF 135 includes (among other N11 parameters used to identify theN11 signaling transaction itself, e.g., including AMF ID or SMF ID orother transaction IDs) the new S-NSSAI (e.g., S-NSSAI-b) to be used bythe UE 205 when the UE 205 re-establishes the PDU session. Here, the AMF135 determines whether to include the new S-NSSAI in the N11 SM Requestmessage based on a need to change Allowed S-NSSAIs configured in the UE205. Considering the set of stored Allowed S-NSSAIs, the AMF 135 (and/orwith NSSF 150) can determine whether the UE 205 may continue to use thesame set of Allowed S-NSSAIs indicated during initial registration. Insome embodiments, however, the previously established PDU session mayneed to be reestablished due to the NSI change (e.g., due to one or moreparameters used to establish the PDU session becomingunavailable/invalid). For example, the AMF 135 may determine that theset of stored Allowed S-NSSAIs does not change; however, the establishedPDU session may still need to be re-established with another S-NSSAIwhich is part of the set of stored Allowed S-NSSAIs due to the change inNSI.

In response to the N11 SM Request message, the first SMF 235 initiatesan N4 release procedure with the first UPF 245 (e.g., UPF-a) in order torelease the user plane resources (see block 516). After the N4 releaseprocedure, the first SMF 245 generates and sends an N11 SM Responsemessage to the AMF 135 (see signaling 518). Here, the N11 SM Responsemessage includes N11 information to be used in the AMF 135 to identifythe N11 signaling transaction itself, (e.g., including AMF ID or SMF IDor other transaction IDs) and an N1 SM Information container thatcontains a PDU Session Release Request message. The PDU Session ReleaseRequest message contains the PDU Session ID (and other parameters foridentifying the PDU session at the UE 205), and in addition a new set ofparameters (e.g., S-NSSAI-b) and an appropriate Cause value for the PDUSession release indicating to the UE 205 that e.g., the PDU session canbe re-established with the new set of parameters (e.g., new S-NSSAI-b).

Referring now to FIG. 5B, when the AMF 135 (and/or NSSF 150) determinesthat a change of the set of Allowed S-NSSAIs associated with the UE 205is needed, there are several situations which may occur about themodification of the Set of Network Slice(s) for a UE (e.g., the UE 205).

In a first embodiment, a Network Slice instance (NSI) becomes no longeravailable to the UE 205 (e.g., due to the change of set of NSIs for theUE). Here, the Network Slice instance corresponds to an S-NSSAI which ispart of the old Allowed NSSAI. In such an embodiment, the AMF 135initiate, e.g., a Registration Management procedure or UE ConfigurationUpdate procedure to send a new Allowed NSSAI which does not contain theunavailable old S-NSSAI (see signaling 520). The UE 205 determines howto use the new parameters based on usage information included with thenew parameters (see block 524). In addition, the network initiates PDUSession Release procedure and indicates that the PDU Session(s) arereleased due to no longer available associated S-NSSAI (see signaling522). In one embodiment, the UE 205 may re-establish the PDU Sessionwith another default S-NSSAI part of the allowed NSSAI (see block 526,signaling 528). In another embodiment, the UE 205 releases the PDUsession and does not initiate PDU Session establishment while theassociated S-NSSAI(s) are not part of the Allowed NSSAI.

In a second embodiment, a new, additional Network Slice instance becomesavailable to the UE 205 (e.g., due to the change of the set of NSIs forthe UE). Here, the new Network Slice instance corresponds to a newS-NSSAI which is not a part of the Allowed NSSAI in the UE 205. In suchan embodiment, the AMF 135 may initiate, e.g., a Registration Managementprocedure or UE Configuration Update procedure to send a new AllowedNSSAI which contains the new additional S-NSSAI (see signaling 520). TheUE 205 determines how to use the new parameters based on usageinformation included with the new parameters (see block 524). Based onUE configurations (e.g., NSSP policies), the UE 205 may initiate a PDUSession release and re-establishment procedures to associate existingPDU Session(s) with the new S-NSSAI, i.e. with the existing PDUSession(s) are established over the new Network Slice instance (seeblock 526, signaling 528).

In a third embodiment, a new Network Slice instance corresponding to aS-NSSAI which is already a part of the Allowed NSSAI becomes availableto the UE 205 (e.g., due to the change of the set of NSIs for the UE),where the new NSI replaces an old NSI used by the UE 205. Here, thenetwork does not need to assign a new Allowed NSSAI to the UE 205.However, the network (e.g., the SMF 235 based on a corresponding triggerfrom the AMF 135 in signaling 514) initiates a PDU Session Releaseprocedure for the PDU Session(s) associated with the impacted S-NSSAI.The PDU Session release request message contains an appropriate Causevalue (e.g., indicating NSI change) and with an indication of thepossibility of re-establishment. Where so indicated, the UE 205 mayre-establish the PDU Session(s) using the same S-NSSAI and the PDUSession will be established over the new Network Slice instance.

In a fourth embodiment, a new Network Slice instance corresponding to aS-NSSAI which is not a part of the Allowed NSSAI becomes available tothe UE 205 due to the change in NSI, where the new NSI replaces an oldNSI used by the UE 205. In such an embodiment, the AMF 135 may initiate,e.g., a Registration Management procedure or UE Configuration Updateprocedure to send a new Allowed NSSAI which contains the new S-NSSAI andindicates that the new S-NSSAI is a replacement to an old S-NSSAI (seesignaling 520). The network (e.g., the SMF 235 based on a correspondingtrigger from the AMF 135 in signaling 514) also initiates a PDU SessionRelease procedure for the PDU Session(s) associated with the old S-NSSAI(see signaling 522). The UE 205 determines how to use the new parametersbased on usage information included with the new parameters (see block524). In certain embodiments, the SMF 235 indicates that the PDU Sessionre-establishment should be performed with the new S-NSSAI (see block526). In such embodiments, the UE 205 re-establishes the PDU Session(s)associated with the old S-NSSAI using the new S-NSSAI (see signaling528).

In the first, second, and fourth embodiments above, the AMF 135 sends tothe UE 205 a new (second) set of parameters to be used after determiningthat one or more parameters in the first set cannot be used anymore (seesignaling 520). In addition to the second set of parameters, the networkmay also send an indication of how a parameter in the first set can bemapped to a parameter in the second set. This is the usage informationdiscussed above, and the UE 205 determines how to use the new parametersfrom the usage information (see block 524).

The NAS signaling from the network (e.g., AMF 135) to the UE can beperformed within different NAS procedures. If the event for NSIreconfiguration is triggered based on a UE-initiated Registration, thenthe AMF 135 may use a NAS Registration Accept message to convey thesecond set of parameters (and usage information). Otherwise, if theevent for NSI reconfiguration is network-initiated (e.g., due todeployment of network slice instances changes or UE subscriptionchanges), then the AMF 135 may use a NAS UE Configuration Updateprocedure, a NAS Notification procedure, or any other NAS procedure forUE parameters configuration update. In this scenario, a NAS proceduretriggered by the network is used to update/modify theconfiguration/parameters of the UE 205.

In one example, the UE 205 receives a NAS Registration Accept message ora NAS Notification message which includes a second set of NSAAIparameters (e.g., S-NSSAI-b), and usage information (e.g., mappinginformation) that maps S-NSSAI-b to S-NSSAI-a (see signaling 520). Inanother example, the UE 205 receives a NAS Registration Accept messageor a NAS Notification message that carries the second set of NSSAIparameters including [S-NSSAI-b, S-NSSAI-c] and the usage informationindicates that [S-NSSAI-b can be mapped to S-NSSAI-a]. Here, S-NSSAI-cmay be a previously Allowed S-NSSAI or may be a new S-NSSAI which doesnot replace a part of the previously Allowed NSSAI.

In certain embodiments, the UE 205 sends in a NAS Registration Requestmessage that includes the Requested NSSAI parameter [S-NSSAI-a,S-NSSA-c] (refer to signaling 508). Here, the AMF 135 may determine thatthe network cannot serve [S-NSSAI-a, S-NSSA-c] due to the change in NSI(refer to block 512). In response, the AMF 135 may send a NASRegistration Accept message with the new Allowed NSSAI [S-NSSAI-x,S-NSSA-y] and usage information for mapping the new Allowed NSSAI to theold Allowed NSSAI. For example, the usage information may indicate that,e.g., S-NSSAI-x maps to S-NSSAI-a, and S-NSSA-y maps to S-NSSAI-c. Inthe case of operator-specific SST values, the usage information mayindicate how the SST values in the set of new Allowed S-NSSAI is mappedto a standard SST value or how the SST values in the set of new AllowedS-NSSAI is mapped an SST value from a Requested S-NSSAI (e.g., SST fromS-NSSAI-x is to be used as the standardized SST value “eMBB”).

Note that the AMF 135 may send a NAS message carrying a PDU sessionrelease request to the UE 205 (see signaling 522), where the PDU sessionrelease request is from a NAS Session Management (SM) message originatedat the first SMF 235. Here, the AMF 135 may receive the PDU sessionrelease request encapsulated within a NAS SM message (e.g., as shown insignaling 518). In certain embodiments, the AMF 135 sends the SM PDUSession Release Request message encapsulated in a NAS RegistrationAccept or encapsulates it in a NAS Notification/Transport message (e.g.,encapsulated as N1 SM Information container parameter). Here, the N1 SMInformation container includes a PDU Session Release Request messagecontaining A) a proper release Cause value indicating a change ofnetwork configuration/slices and B) either an existing old. S-NSSAI or anew S-NSSAI.

Based on the received signaling from the network, the UE 205 determineswhich actions to take. Where a NSI corresponding to an S-NSSAI which ispart of the old allowed NSSAI becomes no longer available, then the UE205 may release the PDU Session associated with the S-NSSAI which is nolonger available. Thereafter, the UE 205 decide to re-establish the PDUSession with another default S-NSSAI part of the allowed NSSAI andaccording to the NSSP configuration (see block 526).

If, however, the S-NSSAI(s) associated with the released PDU Session arenot part of the new Allowed NSSAI, then the UE 205 refrains from thecorresponding application(s) until a new configuration from the networkis performed (e.g., either a new NSSP configuration or a new AllowedNSSAI configuration) which would allow the establishment of thecorresponding data connections (e.g., PDU Sessions). Accordingly, the UE205 does not re-establish the released PDU session until the AllowedNSSAI does not contain an S-NSSAI associated with the application(s).

Where there is a new, additional NSI corresponding to an S-NSSAI whichis not part of the of the old allowed NSSAI, then the UE 205 mayinitiate a PDU Session release procedure and PDU Sessionre-establishment procedure to associate existing PDU Session(s) with thenew S-NSSAI based on UE configurations (e.g., NSSP policies) the UE 205.Accordingly, the PDU Session(s) are moved from one old. NSI to a newNSI. In certain embodiments, the UE 205 may also initiate theestablishment of new PDU Session(s) with a new particular S-NSSAI, forexample in the case that there is configuration in the UE to use the PDUsession with the new S-NSSAI.

Where there is a new NSI corresponding to an S-NSSAI which is already apart of the old allowed NSSAI and the new NSI replaces an old NSI usedby the UE 205, then the UE 205 does not change its NSSAI configuration.However, based on the PDU Session release procedure (e.g., based on theRelease Cause in the PDU Session Release Request message), the UE 205determines that the already established PDU Session may bere-established with the same S-NSSAI value (see block 526). Here, the UE205 may release the established PDU session and initiate a PDU Sessionestablishment procedure with the same S-NSSAI value.

Where there is a new NSI corresponding to an S-NSSAI which is not a partof the old allowed NSSAI and the new NSI replaces an old NSI used by theUE 205, then the UE 205 determines a third set of parameters from thefirst set of parameters and the second set of parameters using the usageinformation. Here, the UE 206 determines how to use the new set ofparameters signaled (see block 524). In one embodiment, the UE 205stores the new second set of parameters including the usage information(e.g., mapping information). In certain embodiments, the UE 205 updatesits NSSAI-related configuration based on the usage information.

As depicted in FIG. 5B, the third set of parameters contains [S-NSSAI-b,DNN-1], where internally the UE 205 maps S-NSSIA-a to S-NSSAI-b for thisregistration area (or this PLMN). In some embodiments, the third set ofparameters is equal to the second set of parameters.

The UE 205 then re-establishes the data connection using the third setof parameters (or initiates a new data connection using a fourth set ofparameters based on the second set of parameters). Here, it is assumedthat the UE 205 successfully completed the NAS Registration procedure(Mobility management procedure) with the network. To re-establish thedata connection, the UE 205 initiates NAS Session Management signalingtowards the network (e.g., towards an SMF).

The NAS SM signaling message (referenced as N1 SM Information) isencapsulated in another NAS message terminated at the AMF 135 (e.g., theNAS Transport message). In certain embodiments, the NAS messageterminated at the AMF 135 contains both a new PDU Session ID and an oldPDU Session ID in order to allow the AMF 135 to make the associationbetween the old PDU Session (which was terminated) and the new requestedPDU session. The new (third) set of parameters can be optionallyincluded in the PDU Session Establishment Request from the UE 205 to thesecond SMF 250 (e.g., SMF-b).

As depicted, the UE 205 may send a NAS session management message, suchas the depicted NAS Transport message, that includes the third set ofparameters (e.g., S-NSSAI-b, DNN-1, PDU Session ID, etc.) and the N1 SMInformation embedding the PDU Session establishment request (e.g.,containing the new S-NSSAI, SSC mode, PDU type, etc.) (see signaling528). Here, the new set of parameters may be included in the NAS messagetargeted to the AMF 135 (e.g., to be processed in the AMF 135), but alsothe new set of parameters can be included in the N1 SM Informationcontainer targeted to the new SMF (e.g., the second SMF 150) which istransparent to the AMF 135.

The AMF 135 processes the NAS message (e.g., NAS Transport message) fromthe UE 205. Based on the new PDU Session ID, the new S-NSSAI information(e.g., S-NSSAI-b), DNN-1 information, and other parameters, the AMF 135selects a SMF to serve the PDU Session, e.g., the AMF 135 may select anew SMF (see block 530), but also may select the SMF-a 235 if the newNSI characterized by the new S-NSSAI is served by SMF-a 235. Asdepicted, the AMF 135 selects the second SMF 250 (“SMF-b”). Afterselecting the SMF to serve the PDU Session, the AMF 135 forwards the NASSM message to the selected second. SMF 250 (see signaling 532). Asdepicted, the AMF 135 may send a N11 SM request message that containsthe PDU Session ID and the N1 SM information embedding the PDU SessionEstablishment Request. Note that the PDU session establishment requestincludes the new S-NSSAI-b, DNN-1, SSC1, PDU type, etc.

The second SMF 250 processes the NAS SM message and selects anappropriate UPF (here, the second UPF 255). After selecting the new UPF,the second SMF 250 establishes the N4 association with the second UPF255 and configures the second UPF 255 correspondingly (see block 534).After establishing the N4 association, the second SMF 250 generates andsends to the AMF 135 an N11 SM response message including PDU SessionID, N2 SM Information (e.g., PDU Session ID, QoS profiles(s), UP tunnelInfo, etc.), N1 SM Information (e.g., PDU Session Establishment Accept(IP configuration info (IP prefix/address), Authorized QoS Rule(s),S-NSSAI, NSSAI assistance information, SSC mode, etc.), and otherparameters.

The second SMF 250 sends the N11 message to the AMF 135 (see signaling536) and the AMF 135 forwards the N2 SM information to the (R)AN and theN1 SM Information to the UE (see signaling 538). The usage information(e.g., NSSAI assistance information) in the N1 SM information (e.g., PDUSession Establishment Accept) message may be the same or different fromthe usage information provided in the NAS Registration/Mobilitysignaling (refer to signaling 520). For example, the usage informationin the N1 SM information message may indicate to the UE 205 which(additional) application IDs can be used with the S-NSSAI from the PDUSession Establishment Accept message.

In some embodiments, the NSSF 150 is responsible for the association ofthe UE 205 with a particular set of NSIs. For example, in a givenregistration area, the NSSF 150 may determine to which NSI a particularS-NSSAI maps. Here, the NSSF 150 is responsible for the associationbetween S-NSSAI and NSI. Accordingly, the AMF 135 may consult the NSSF150 when the UE 205 performs a Registration procedure (with or withoutRequested NSSAI). Here, the AMF 135 requests the NSSF 150 to determinewhich NSI(s) to use for the UE 205 for the set of Allowed NSSAIs.

In certain embodiments, each NSI is identified by an Identifier (e.g.,NSI-ID) which may be used by the network internally, but not exposed tothe UE 205. Here, when the AMF 135 receives a new NAS RegistrationRequest from the UE 205, the AMF 135 derives a “preliminary set” ofAllowed S-NSSAIs based on the set of Requested S-NSSAIs and UE 205'ssubscription information. Then the AMF 135 sends this “preliminary set”of Allowed S-NSSAIs to the NSSF 150 to request possible NSIs to be usedin this registration area. In response, the NSSF 150 determines the NSIsbased on the “preliminary set” of Allowed S-NSSAIs and the actualNetwork Slice deployment configuration in this area. In certainembodiments, the NSSF 150 determines that two S-NSSAIs from the“preliminary set” of Allowed S-NSSAIs are mapped to the same NSI. TheNSSF 150 returns to the AMF 135 the mapping of S-NSSAIs to NSI-IDs.Based on this information, the AMF 135 derives the “actual set” ofAllowed S-NSSAIs to be transmitted to the UE 205.

FIG. 6 depicts a method 600 for reconfiguring a data connection with newparameters, according to embodiments of the disclosure. In someembodiments, the method 600 is performed by an apparatus, such as theremote unit 105, the UE 205, and/or the remote apparatus 300. In certainembodiments, the method 600 may be performed by a processor executingprogram code, for example, a microcontroller, a microprocessor, a CPU, aGPU, an auxiliary processing unit, a FPGA, or the like.

The method 600 begins and establishes 605 a data connection with amobile communication network using a first set of parameters. In oneembodiment, the first set of parameters includes a network sliceselection parameter and a data network name.

The method 600 includes receiving 610 a second set of parameters fromthe mobile communication network and an indication of how at least oneparameter in the first set of parameters (e.g., the set used toestablish the data connection) corresponds to at least one new parameterin the second set. In some embodiments, the first set of parametersincludes a first network slice selection parameter. In such embodiments,the second set of parameters includes one or more new network sliceselection parameters.

In some embodiments, receiving 610 the indication of how the at leastone parameter in the first set corresponds to at least one new parameterin the second set includes receiving usage information that associatesthe one or more new network slice selection parameters with one or morepreviously provided network slice selection parameters. Here, the one ormore previously provided network slice selection parameters includes thefirst network slice selection parameter. In certain embodiments,receiving 610 the second set of parameters includes updating a networkslice selection configuration of a remote unit based on the one or morenew network slice selection parameters.

In some embodiments, receiving 610 the second set of parameters includesreceiving an indication that at least one parameter in the first set(e.g., used to establish the data connection) is no longer valid. In oneembodiment, receiving 610 the indication that at least one parameter inthe first set is no longer valid includes receiving an indication thatthe data connection is discontinued (e.g., released).

In certain embodiments, receiving 610 the second set of parametersoccurs in response to sending a registration request to update themobile communication network with a new registration area. In oneembodiment, receiving 610 the second set of parameters and theindication of how the at least one parameter in the first setcorresponds to at least one new parameter in the second set includesreceiving a configuration update message. In another embodiment,receiving 610 the second set of parameters and the indication of how theat least one parameter in the first set corresponds to at least one newparameter in the second set includes receiving a NAS notificationmessage. In yet another embodiment, receiving 610 the second set ofparameters and the indication of how the at least one parameter in thefirst set corresponds to at least one new parameter in the second setincludes receiving a NAS Registration Accept message.

The method 600 includes determining 615 a third set of parameters fromthe first set of parameters and the second set of parameters. In oneembodiment, determining 615 the third set of parameters from the firstset of parameters and the second set of parameters includes replacing atleast one invalid parameter in the first set with at least onecorresponding parameter in the second set to form the third set ofparameters.

The method 600 includes reconfiguring 620 the data connection using thethird set of parameters. In certain embodiments, reconfiguring 620 thedata connection includes performing one of: re-establishing the dataconnection using the third set of parameters, establishing a new dataconnection using a fourth set of parameters based on the second set ofparameters, and releasing the data connection.

In some embodiments, reconfiguring 620 the data connection includesre-establishing the data connection using the third set of parameters.In one embodiment, re-establishing the data connection includes sendinga NAS session management message, the NAS session management messagecontaining the third set of parameters. The method 600 ends.

FIG. 7 depicts a method 700 for re-registering a remote unit with newparameters, according to embodiments of the disclosure. In someembodiments, the method 700 is performed by an apparatus, such as theAMF 135 and/or network function apparatus 400. In certain embodiments,the method 700 may be performed by a processor executing program code,for example, a microcontroller, a microprocessor, a CPU, a GPU, anauxiliary processing unit, a FPGA, or the like.

The method 700 begins and registers 705 a remote unit with a mobilecommunication network using a first set of parameters. In someembodiments, registering 705 the remote unit includes receiving aninitial registration message from the remote unit and returning anallowed set of network slice selection parameters to the remote unit.Here, the initial registration message contains a requested set ofnetwork slice selection parameters. In certain embodiments, the allowedset of network slice selection parameters includes one or more defaultnetwork slice selection parameters. Further, returning the allowed setof network slice selection parameters may include sending an indicationthat a default network slice selection parameter corresponds to a datanetwork name and/or a standardized network slice type.

The method includes identifying 710 a second set of parameters to beused by the remote unit in the mobile communication network. In oneembodiment, identifying 710 the second set of parameters includesidentifying the second set of parameters based on the requested set ofnetwork slice selection parameters, subscribed parameters of the remoteunit, and/or a network slice instance associated with the remote unit.In another embodiment, identifying 710 the second set of parametersincludes identifying the second set of parameters based on aconfiguration of the remote unit and a network slice instance currentlyassociated with the remote unit.

In some embodiments, the first set of parameters includes a firstnetwork slice selection parameter and identifying 710 the second set ofparameters includes identifying one or more new network slice selectionparameters for a network slice instance currently associated with theremote unit. In some embodiments, identifying 710 the second set ofparameters to be used by the remote unit in the mobile communicationnetwork includes sending a query to a network slice selection functionin response to receiving a registration request from the remote unit andreceiving, from the network slice selection function, a mapping ofnetwork slice selection parameters to network slice instances. Here,identifying 710 the second set of parameters further includesidentifying a set of allowed network slice selection parameters based ona network slice instance currently associated with the remote unit.

In one embodiment, identifying 710 the second set of parameters includesreceiving a registration request from the remote unit and determiningthat at least one parameter in a first set of parameters is no longervalid occurs in response to the registration request. In certainembodiments, the registration request is received in response to one of:the remote unit changing its registration area, the remote unit changingits PLMN change, and the remote unit requiring temporarily use a networkslice. In another embodiment, identifying 710 the second set ofparameters includes determining that at least one parameter in a firstset of parameters is no longer valid in response to one of: a change insubscription of the remote unit, a change in network policy ruleapplicable to the remote unit, and a change in network slice deployment.

The method includes sending 715 a second set of parameters to the remoteunit and an indication of how the at least one parameter in the firstset of parameters corresponds to at least one new parameter in thesecond set. In one embodiment, sending 715 the indication of how the atleast one parameter in the first set corresponds to at least one newparameter in the second set includes sending usage information thatassociates the one or more new network slice selection parameters withone or more previously provided network slice selection parameters.Here, the one or more previously provided network slice selectionparameters may include the first network slice selection parameter. Incertain embodiments, the usage information is sent in response todetermining that the new parameter in the second set is not known to theremote unit.

In certain embodiments, sending 715 the second set of parameters and theindication of how the at least one parameter in the first setcorresponds to at least one new parameter in the second set includessending a registration accept message (e.g., a NAS Registration Acceptmessage) that includes the second set of parameters and the indicationof how the at least one parameter in the first set corresponds to atleast one new parameter in the second set. In other embodiments, sending715 the second set of parameters and the indication of how the at leastone parameter in the first set corresponds to at least one new parameterin the second set includes sending one of: a configuration updatemessage and a NAS notification message.

The method includes receiving 720 a message from the remote unitcontaining a third set of parameters for registering with the mobilecommunication network. Here, the third set of parameters is based on thefirst set of parameters and the second set of parameters. In someembodiments, receiving 720 the message from the remote unit includesreceiving a session management (“SM”) request message encapsulated in aNAS transport message. Here, the NAS transport message contains thethird set of parameters and the session management message, with the SMrequest message including the at least one new parameter from the secondset of parameters, such as a new network slice selection parameter.

In certain embodiments, identifying 710 the second set of parametersincludes sending a SM request message to a SM function in response todetermining that at least one parameter in the first set is no longervalid. Here, the SM request message includes an indication to release anestablished data connection and a new network slice selection parameterfrom the second set of parameters, such as a new network slice selectionparameter. Sending the SM request message may include receiving an SMresponse message from the SM function, the SM response messagecontaining a session release request message for the established dataconnection, and sending the session release request message to theremote unit. The method 700 ends.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

The invention claimed is:
 1. An apparatus comprising: a transceiver thatcommunicates with a mobile communication network; and a processor that:registers with the mobile communication network using a first set ofnetwork slice selection parameters, the first set of network sliceselection parameters based on a UE configuration; receives a second setof network slice selection parameters from the mobile communicationnetwork; receives mapping information from the mobile communicationnetwork, wherein the mapping information indicates how a network sliceselection parameter in the second set of network slice selectionparameters corresponds to a network slice selection parameter of thefirst set of network slice selection parameters; and uses the second setof network slice selection parameters and the mapping information whenestablishing a data connection for an application.
 2. The apparatus ofclaim 1, wherein the first set of network slice selection parametersincludes a first network slice selection parameter, wherein the secondset of network slice selection parameters comprises one or more newnetwork slice selection parameters.
 3. The apparatus of claim 2, whereinreceiving the mapping information comprises receiving usage informationthat associates the one or more new network slice selection parameterswith one or more previously provided network slice selection parameters,wherein the one or more previously provided network slice selectionparameters includes the first network slice selection parameter.
 4. Theapparatus of claim 1, wherein the processor further sends a registrationrequest to update the mobile communication network with a newregistration area, wherein the processor receives the second set ofnetwork slice selection parameters in response to the registrationrequest.
 5. The apparatus of claim 1, wherein the transceiver receives anon-access stratum (“NAS”) UE configuration update message from themobile communication network, wherein the NAS UE configuration updatemessage includes the second set of network slice selection parametersand the mapping information.
 6. The apparatus of claim 1, wherein thetransceiver receives a non-access stratum (“NAS”) notification messagefrom the mobile communication network, wherein the NAS notificationmessage includes the second set of network slice selection parametersand the mapping information.
 7. The apparatus of claim 1, wherein thetransceiver receives a non-access stratum (“NAS”) Registration Acceptmessage includes the second set of network slice selection parametersand the mapping information.
 8. The apparatus of claim 1, wherein theprocessor updates the UE configuration by replacing at least oneparameter in the first set with at least one corresponding parameter inthe second set, wherein the at least one corresponding parameter in thesecond set is determined by using the mapping information.
 9. Theapparatus of claim 1, wherein the first set of network slice selectionparameters comprises a first set of Single Network Slice SelectionAssistance Information values (“S-NSSAIs”) that are derived from the UEconfiguration.
 10. The apparatus of claim 1, wherein the data connectioncomprises a Protocol Data Unit (“PDU”) Session, wherein the processorselects a network slice using the second set of network slice selectionparameters and the mapping information in response to one of:determining to establish a PDU Session and determining to send user dataover an established data PDU Session.
 11. A method comprising:registering with a mobile communication network using a first set ofnetwork slice selection parameters, the first set of network sliceselection parameters based on a UE configuration; receiving a second setof network slice selection parameters from the mobile communicationnetwork; receiving mapping information from the mobile communicationnetwork, wherein the mapping information indicates how a network sliceselection parameter in the second set of network slice selectionparameters corresponds to a network slice selection parameter of thefirst set of network slice selection parameters; and using the secondset of network slice selection parameters and the mapping informationwhen establishing a data connection for an application.
 12. The methodof claim 11, wherein the first set of network slice selection parametersincludes a first network slice selection parameter, wherein the secondset of network slice selection parameters comprises one or more newnetwork slice selection parameters.
 13. The method of claim 12, whereinreceiving the mapping information comprises receiving usage informationthat associates the one or more new network slice selection parameterswith one or more previously provided network slice selection parameters,wherein the one or more previously provided network slice selectionparameters includes the first network slice selection parameter.
 14. Themethod of claim 11, wherein receiving the second set of network sliceselection parameters and the mapping information comprises receiving aregistration accept message that includes the second set of networkslice selection parameters and an indication of how the at least oneparameter in the first set corresponds to at least one new parameter inthe second set.
 15. The method of claim 11, wherein receiving the secondset of network slice selection parameters and the mapping informationcomprises receiving a non-access stratum (“NAS”) UE configuration updatemessage from the mobile communication network, wherein the NAS UEconfiguration update message includes the second set of network sliceselection parameters and the mapping information.
 16. The method ofclaim 11, wherein receiving the second set of network slice selectionparameters and the mapping information comprises receiving a non-accessstratum (“NAS”) notification message from the mobile communicationnetwork, wherein the NAS notification message includes the second set ofnetwork slice selection parameters and the mapping information.
 17. Themethod of claim 11, wherein receiving the second set of network sliceselection parameters and the mapping information comprises the processorreceiving a non-access stratum (“NAS”) Registration Accept message fromthe mobile communication network, wherein the NAS Registration Acceptmessage includes the second set of network slice selection parametersand the mapping information.
 18. The method of claim 11, furthercomprising updating the UE configuration by replacing at least oneinvalid parameter in the first set with at least one correspondingparameter in the second set, wherein the at least one correspondingparameter in the second set is determined by using the mappinginformation.
 19. The method of claim 11, wherein the first set ofnetwork slice selection parameters comprises a first set of SingleNetwork Slice Selection Assistance Information values (“S-NSSAIs”) thatare derived from the UE configuration.
 20. The method of claim 11,wherein the data connection comprises a Protocol Data Unit (“PDU”)Session, the method further comprising selecting a network slice usingthe second set of network slice selection parameters and the mappinginformation in response to one of: determining to establish a PDUSession and determining to send user data over an established data PDUSession.